David Karich

Then you'll get two hearts. 😅

Fantastic. You've already won my heart. 🤩 P.S.: @Peter Knight, this raises another question for me: have you also planned a ‘delete protection’ feature? When an image is deleted from the Media Hub, is it first checked to see whether the image is used on any pages? If so, deletion is not possible and there is an option to list all the pages where the image is used?

Hi @Peter Knight Thank you very much for the pre-analysis. 😊 It is correct that the sheer number of pages is not the problem. I have already achieved good performance in tests with half a million pages. The real problem occurs more during output: the limit here is often the RAM limit of the PHP process. Example: You have an image field for a gallery. In this gallery (here as an example from one of my customers, an event), there are easily between 100 and 200 images per input field. When outputting to the front end – and also in the back end when editing – you run into a MAX RAM problem and very long loading times, as each image object is loaded into the RAM. Here, I now see an additional problem with the ‘1 asset per page’ approach: not only is the image object loaded, but also the complete page object where the asset is stored. And if I understand your concept correctly, the master page object of the asset is also loaded. This means, to stick with the example, that with 100 images, around 300 objects are loaded into RAM just to output them. This is overkill for most servers (especially shared hosting). One possible solution here would be to implement a kind of ‘getRaw()’ method, similar to ‘findRaw()’, which returns all asset paths (including variation paths) and descriptions as a simple array – without the complete object. This would make it easy to iterate over the array and output the images directly. I am aware that this would then make it impossible to use ‘size()’, ‘width()’ etc. and all the image methods. What do you think of this option for special use cases with many assets that need to be loaded at once? And thank you again for your truly great work and your ambition to develop such a complex module!

It looks fantastic so far. Great work. 😯 I'm currently struggling with similar problems and requirements for a media manager. However, it needs to be scalable enough to easily handle 100,000 assets (for a news portal). My experiments with the principle that each asset is also its own page quickly reached the limits of performance. I am therefore pursuing the approach of storing the actual asset paths in the database, i.e. as a JSON object in a separate input field. A well-known problem: what happens if you rename the asset in the file system? I am still in the testing phase to see if this can be solved with a simple SQL replace and update. However, I would be very happy to test your module. Maybe I don't have to reinvent the wheel after all. 🙂 Here are a few more wishes that I have as requirements in my projects: Folders: Customers love folders and folder trees. Multiple use: An asset is used multiple times on different pages; it must also be possible to have different descriptions here. With the MM module, for example, the description is global and cannot be changed individually for each reference. Language versions: An asset is only available for certain language versions, so it can be deactivated for EN, for example, and will not be displayed in this language in the frontend. Automatic categorisation: An API that enables automatic categorisation after uploading/saving. Example: In the ‘News’ template, there is a select field called ‘Category’. If a new image is uploaded in the edit mode of the page, it should be automatically loaded into the folder of the selected category or alternatively tagged. In the best case, this creates an automatic structure if you can define several fields such as ‘News/2026/Category’. The date is read from a date field and the category from a select field, etc.

@Gadgetto Are you still developing your module further with regard to the switch to Snipcart V3?

Hi @kongondo Happy New Year. It's been a while since anything has happened here on the subject of ‘Next’. Since there are two major projects planned for this year where I would be needed for MM, I wanted to ask what the status is? 😊

AIOM is alive 🙃 I am pleased to announce that the AIOM module will be further developed and supported by @matjazp. My original repository is now archived, and matjazp's fork is now the official one. The forked version is now also listed in the Processwire module directory. This should make it possible for everyone to update the old version to the new one, either manually or via the ProcessWire upgrade module.

@matjazp Thank you for your work and for keeping the module alive. We can talk about adding you as an owner in the Git repo so that the module can be further developed. If you're interested, just get in touch with me.

Hi Nick, no. I have experimented myself and got it to work in parts, but the whole OAuth setup from Microsoft is just annoying. I now send via SMTP relays, for example Amazon SES. It's cheap, easy to set up and also avoids Microsoft's sending limits. 😊

Thanks @ryan works perfectly and so easy.

Hi @ryan, as I am actively working on updates, I am now at the point where I would like to use the versions. Now I have exactly the problem that the automatically by my module added field "phits" is versioned. But it should not. I know I can explicitly select fields during the restore and could omit this field, but this is not practicable for the users and they forget about it. And suddenly all the statistics are gone. Unfortunately, I also can't find any info on whether I can hook into "$pagesVersions->restorePageVersion" or "$pagesVersions->savePageVersion" to always skip the "phits" field. Do you have any other idea how I can tell the module that it should not be versionable? The field is just a very simple fieldtype: https://github.com/flipzoom/PageHitCounter/blob/master/FieldtypePageHitCounter.module Thank you and best regards

Hi @FireWire First of all, thank you for the module and all the work you have put into it! I just wanted to test the module in a real world project, but quickly realised that certain terms are always translated incorrectly by Deepl. In the web version this is easy to solve with the personal glossary. Is there also a way to create a glossary here, or to tell the API in some way to use my glossary from my account?

Unfortunately, that's how I understood it and I didn't understand it. Actually, all the real gamechanger proposals were rejected, especially the ones that so many people have been asking for years. At its core, PW is obviously tied to what Ryan needs it for, not the community.

Yes, exactly. I am also aware that there is still some time left, but I don't want to delay the situation until the last minute, because many customers have and send via Office365. ?

I think the most talked about feature is an asset manager. The drilling down of file and imagefields so that you can choose assets from a global library that have already been uploaded somewhere, instead of having to upload assets multiple times. Actually, the approach using references is the best I've come across so far. The data remains where it was originally uploaded, but is only referenced in a file/image field on another page.